約 5,102,936 件
https://w.atwiki.jp/cod4mod/pages/31.html
MP Fast Files (.csv) The purpose of this section is to outline what is needed to create the .csv files used in a multiplayer map. A .csv file basically defines the files that need to be pre-loaded into memory for the map to work properly. この項の目的は何がマルチプレ-ヤーマップで使われた .csv ファイルを作るために必要とされるかについて概説することです。.csv ファイルが基本的にマップが適切に機能するために記憶装置の中にプリによってロードされた必要があるファイルを定義します。 Creating the level.csv file The first step is to create a fast file with your level s name in the filename. It goes in the following game directory 第１ステップはファイル名であなたのレベルの名前を持った高速のファイルを作成するはずです。それは次のゲームディレクトリに入ります： \zone_source\mp_yourmap.csv Below is a screenshot of the mp_backlot.csv file, opened in Excel. It can be opened in any text editing application. Below the image is a breakdown of lines from the file. 下は、エクセルで開かれて、 mp_backlot.csv ファイルのスクリーンショットです。それはどんなテキスト編集アプリケーションででも開かれることができます。下の画像はファイルからのラインの内訳です。 ignore code_post_gfx_mp Needed for the map to run. ignore common_mp Needed for the map to run. ignore localized_code_post_gfx_mp Needed for the map to run. ignore localized_common_mp Needed for the map to run. 無視 code_post_gfx_mp マップを求めて走るために必要とされます。 無視 common_mp マップを求めて走るために必要とされます。 無視 localized_code_post_gfx_mp マップを求めて走るために必要とされます。 無視 localized_common_mp マップを求めて走るために必要とされます。 material compass_map_mp_backlot This loads the minimap image material into memory. Needed to get a minimap image to show up, in addition to the line from the level.gsc file. col_map_mp maps/mp/mp_backlot.d3dbsp References the BSP map file, the file generated when a map is compiled. Needed for the map to run. 資料 compass_map_mp_backlot これは記憶装置の中にミニマップイメージ資料をロードします。ミニマップイメージに level.gsc ファイルからラインまで、付加で、現われるようにさせるために必要とされます。 col_map_mp maps/mp/mp_backlot.d3dbsp References 、ＢＳＰマップファイル、マップが編集されるとき、生成されたファイル。マップを求めて走るために必要とされます。 rawfile maps/mp/mp_backlot.gsc References the map script file. Needed for the map to run properly. rawfile maps/mp/mp_backlot_fx.gsc References the map effects file. Needed if the level has a level_fx.gsc file. rawfile maps/createfx/mp_backlot_fx.gsc This line shouldn t be used for a user-made map. rawfile maps/createart/mp_backlot_art.gsc This line shouldn t be used for a user-made map. rawfile maps/mp/mp_backlot.gsc References 、マップスクリプトファイル。マップを求めて適切に走るために必要とされます。 maps/mp/mp_backlot_fx.gsc References マップ効果が提出する rawfile 。もしレベルが level_fx.gsc ファイルを持っているなら、必要とされます。 ラインがそうであるべきでない maps/createfx/mp_backlot_fx.gsc This がユーザ製のマップのために使った rawfile 。 ラインがそうであるべきでない maps/createart/mp_backlot_art.gsc This がユーザ製のマップのために使った rawfile 。 sound common mp_backlot !all_mp Loads in sounds defined for mp_backlot. The ! before all_mp is important, otherwise all sounds will be loaded in and the map probably won t load. sound generic mp_backlot !all_mp sound voiceovers mp_backlot !all_mp sound multiplayer mp_backlot !all_mp 健全な普通の mp_backlot ! all_mp mp_backlot を求めて定義された音でロードします。all_mp の前の！は重要です、さもなければ音がロードされるであろうすべてとマップがおそらくロードしないでしょう。 健全な一般的な mp_backlot ! all_mp 音ナレーション mp_backlot ! all_mp 音マルチプレ-ヤー mp_backlot ! all_mp impactfx mp_backlot Needed for the map to run properly. xmodel weapon_saw_mg_setup Used if the map has a mounted turret somewhere in it. include mptypes_desert Loads in desert MP Types. This line has to match the definition in the level.gsc file. impactfx mp_backlot マップを求めて適切に走るために必要とされます。 xmodel weapon_saw_mg_setup 、もしマップがそれのどこかでマウントされた銃架を持っているなら、使われます。 インクルード mptypes_desert 砂漠のＭＰタイプでロードします。このラインは level.gsc ファイルで定義と一致しなければなりません。 fx misc/bird_seagull_flock_large This is how a special effect from the level_fx.gsc file is loaded into memory. fx misc / bird_seagull_flock_large これは level_fx.gsc ファイルからの特殊効果がどのように記憶装置の中にロードされるかです。 Defining destructible cars in the level.csv file Destructible cars are placed in Radiant from a special prefab directory. For instance, to place the Green Sedan 1 destructible car, you d place the following prefab in your map 自動車が特別なプレハブディレクトリから明るく置かれる Destructible 。実例、場所に緑の箱型自動車１ destructible 自動車を求めて、あなたは次のプレハブをあなたのマップに置くでしょう： \map_source\prefabs\mp_destructibles\vehicle_80s_sedan1_green_destructible.map Then in your level.csv file, you d define these lines for all the Sedan 1 cars (regardless of the color) それからあなたの level.csv ファイルで、あなたはすべての箱型自動車１自動車を求めて（色にかかわらず）これらのラインを定義するでしょう： xmodel vehicle_80s_sedan1_glass_f xmodel vehicle_80s_sedan1_glass_lf xmodel vehicle_80s_sedan1_glass_lb xmodel vehicle_80s_sedan1_glass_rf xmodel vehicle_80s_sedan1_glass_rb xmodel vehicle_80s_sedan1_glass_b xmodel vehicle_80s_sedan1_glass_f_dam xmodel vehicle_80s_sedan1_glass_lf_dam xmodel vehicle_80s_sedan1_glass_lb_dam xmodel vehicle_80s_sedan1_glass_rf_dam xmodel vehicle_80s_sedan1_glass_rb_dam xmodel vehicle_80s_sedan1_glass_b_dam For the Green Sedan 1 car specifically, you d also put the following lines in your level.csv file 緑の箱型自動車１自動車を求めて特に、あなたは同じく（すでに）あなたの level.csv ファイルに次のラインを入れていました： xmodel vehicle_80s_sedan1_green_hood xmodel vehicle_80s_sedan1_green_hood_dam xmodel vehicle_80s_sedan1_green_trunk xmodel vehicle_80s_sedan1_green_trunk_dam xmodel vehicle_80s_sedan1_green_wheel_lf xmodel vehicle_80s_sedan1_green_door_lf xmodel vehicle_80s_sedan1_green_door_lb xmodel vehicle_80s_sedan1_green_door_rf xmodel vehicle_80s_sedan1_green_door_rb xmodel vehicle_80s_sedan1_green_bumper_f xmodel vehicle_80s_sedan1_green_bumper_b xmodel vehicle_80s_sedan1_green_mirror_l xmodel vehicle_80s_sedan1_green_mirror_r xmodel vehicle_80s_sedan1_green_light_lf xmodel vehicle_80s_sedan1_green_light_lf_dam xmodel vehicle_80s_sedan1_green_light_lb xmodel vehicle_80s_sedan1_green_light_lb_dam xmodel vehicle_80s_sedan1_green_light_rf xmodel vehicle_80s_sedan1_green_light_rf_dam xmodel vehicle_80s_sedan1_green_light_rb xmodel vehicle_80s_sedan1_green_light_rb_dam xmodel vehicle_80s_sedan1_green_destroyed Be aware that each type of destructible car you use (car type / color combo) uses up a significant amount of memory. So you should start by adding only one type of car throughout your map, then gradually add variety to the map. あなたが使うそれぞれのタイプの destructible 自動車（自動車タイプ / カラーコンボ）がかなりの量のメモリを使うことを知っていてください。それであなたは、あなたのマップを通じて自動車のたった１つのタイプを加えることによって、始めて、それから次第にマップに多様性を加えるべきです。 Creating the level_load.csv file The level_load.csv should also be created in order for the map to work properly. It goes in the same directory as the level.csv level_load.csv は同じくマップが適切に機能するために作られるべきです。それは level.csv と同じディレクトリに入ります： \zone_source\mp_yourmap_load.csv Below is a screenshot of mp_backlot_load.csv. A user-made map should have the same values, with the bottom value replaced to have the name of the custom map instead of mp_backlot. 下は mp_backlot_load.csv のスクリーンショットです。ユーザ製のマップが mp_backlot の代わりにカスタムマップの名前を持つために、置き換えられた最下段値で、同じ文字を持っているべきです。 (Original "http //www.infinityward.com/wiki/index.php?title=MP_Fast_Files") 名前 すべて読む
https://w.atwiki.jp/skmt200x/pages/108.html
ヘッダ Section 1 Global EnvironmentServer HTTP応答ヘッダの設定 サーバ設定ファイルのルートディレクトリの指定 PIDファイルのパス タイムアウト時間 キープアライブ 最大キープアライブリクエスト数 キープアライブタイムアウト時間 (調査・編集中)先行してforkを行うWEBサーバの設定 (調査・編集中) 待ち受けポート番号 モジュール読み込み 外部設定ファイルの読み込み 拡張ステータス情報保存の有無 実行ユーザ・グループ Section 2 'Main' server configurationサーバ管理者メールアドレス サーバ名 (サーバが自分自身の名前とポートを決定する方法の設定 ドキュメントルートの定義 (調査・編集中) ドキュメントルート配下に適用される設定 ユーザディレクトリモジュールの設定 ユーザディレクトリ配下に適用される設定 ディレクトリインデックスの設定 分散設定ファイルの設定 (調査・編集中) MIMEタイプ設定ファイル デフォルトのMIMEタイプの設定 MIME MAGICモジュールの設定 DNSルックアップの設定 メモリマッピングの有無 sendfileサポートの有無 エラーログの設定 ログレベルの設定 ログフォーマットの設定 (調査・編集中) カスタムログの設定 カスタムログファイルの設定 カスタムログファイルの設定 サーバ生成ドキュメントのフッタの設定 アイコン画像ディレクトリの設定 アイコン画像ディレクトリに適用される設定 Web DAVモジュールの設定 (調査・編集中) CGIディレクトリの設定 ディレクトリインデックスの設定 (調査・編集中) アイコン画像の設定（設定ごとの関連付け） アイコン画像の設定（拡張子ごとの関連付け） デフォルトのアイコン画像の設定 (調査・編集中) (調査・編集中) インデックス対象外の設定 言語の設定 言語優先順位の設定 (調査・編集中) デフォルトの文字セットの設定 (調査・編集中) (調査・編集中) (調査・編集中) (調査・編集中) (調査・編集中) (調査・編集中) (調査・編集中) (調査・編集中) (調査・編集中) (調査・編集中) エラードキュメントの設定 (調査・編集中) サーバステータス表示設定 サーバ情報表示設定 プロキシモジュールの設定 プロキシ経由アクセス時のViaヘッダの有効・無効の設定 コンテンツキャッシュストレージ管理モジュールの設定 Section 3 Virtual Hosts TOPへ編集 ヘッダ # # This is the main Apache server configuration file. It contains the # configuration directives that give the server its instructions. # See URL http //httpd.apache.org/docs/2.2/ for detailed information. # In particular, see # URL http //httpd.apache.org/docs/2.2/mod/directives.html # for a discussion of each configuration directive. # # # Do NOT simply read the instructions in here without understanding # what they do. They re here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # The configuration directives are grouped into three basic sections # 1. Directives that control the operation of the Apache server process as a # whole (the global environment ). # 2. Directives that define the parameters of the main or default server, # which responds to requests that aren t handled by a virtual host. # These directives also provide default values for the settings # of all virtual hosts. # 3. Settings for virtual hosts, which allow Web requests to be sent to # different IP addresses or hostnames and have them handled by the # same Apache server process. # # Configuration and logfile names If the filenames you specify for many # of the server s control files begin with "/" (or "drive /" for Win32), the # server will use that explicit path. If the filenames do *not* begin # with "/", the value of ServerRoot is prepended -- so "logs/foo.log" # with ServerRoot set to "/etc/httpd" will be interpreted by the # server as "/etc/httpd/logs/foo.log". # TOPへ編集 Section 1 Global Environment ### Section 1 Global Environment # # The directives in this section affect the overall operation of Apache, # such as the number of concurrent requests it can handle or where it # can find its configuration files. # Server HTTP応答ヘッダの設定 # # Don t give away too much information about all the subcomponents # we are running. Comment out this line if you don t mind remote sites # finding out what major optional modules you are running ServerTokens OS HTTP応答ヘッダの出力が「Server Apache/2.0.41 (Unix)」のように、OSの情報を含む形式で出力される。 参考 http //www.apache.jp/manual/mod/core.html#servertokens サーバ設定ファイルのルートディレクトリの指定 # # ServerRoot The top of the directory tree under which the server s # configuration, error, and log files are kept. # # NOTE! If you intend to place this on an NFS (or otherwise network) # mounted filesystem then please read the LockFile documentation # (available at URL http //httpd.apache.org/docs/2.2/mod/mpm_common.html#lockfile ); # you will save yourself a lot of trouble. # # Do NOT add a slash at the end of the directory path. # ServerRoot "/etc/httpd" 通常RHEL系OSの設定では、/etc/httpdを指定する。 設定ファイル中の相対パスは、このベースディレクトリからの相対パスになる。 PIDファイルのパス # # PidFile The file in which the server should record its process # identification number when it starts. # PidFile run/httpd.pid タイムアウト時間 # # Timeout The number of seconds before receives and sends time out. # Timeout 120 それぞれの処理（イベント）について、リクエストを失敗させるまでにサーバが待つ時間。 GETリクエストを受け取るのにかかる総時間 POSTやPUTリクエストにて、TCPパケットが届くまでの待ち時間 レスポンスを返す際、TCPのACKが帰ってくるまでの時間 参考 http //www.apache.jp/manual/mod/core.html#timeout参考 http //www.apache.jp/manual/mod/core.html#timeout キープアライブ # # KeepAlive Whether or not to allow persistent connections (more than # one request per connection). Set to "Off" to deactivate. # KeepAlive Off １回のページのリクエストで、沢山のHTTPリクエストを発行する必要がある場合、キープアライブはOnに設定した方がパフォーマンスは向上する。 参考 http //www.apache.jp/manual/mod/core.html#keepalive 最大キープアライブリクエスト数 # # MaxKeepAliveRequests The maximum number of requests to allow # during a persistent connection. Set to 0 to allow an unlimited amount. # We recommend you leave this number high, for maximum performance. # MaxKeepAliveRequests 100 参考 http //www.apache.jp/manual/mod/core.html#maxkeepaliverequests キープアライブタイムアウト時間 # # KeepAliveTimeout Number of seconds to wait for the next request from the # same client on the same connection. # KeepAliveTimeout 15 (調査・編集中) ## ## Server-Pool Size Regulation (MPM specific) ## 先行してforkを行うWEBサーバの設定 # prefork MPM # StartServers number of server processes to start # MinSpareServers minimum number of server processes which are kept spare # MaxSpareServers maximum number of server processes which are kept spare # ServerLimit maximum value for MaxClients for the lifetime of the server # MaxClients maximum number of server processes allowed to start # MaxRequestsPerChild maximum number of requests a server process serves IfModule prefork.c StartServers 8 MinSpareServers 5 MaxSpareServers 20 ServerLimit 256 MaxClients 256 MaxRequestsPerChild 4000 /IfModule 参考 http //httpd.apache.org/docs/2.2/ja/mod/prefork.html (調査・編集中) # worker MPM # StartServers initial number of server processes to start # MaxClients maximum number of simultaneous client connections # MinSpareThreads minimum number of worker threads which are kept spare # MaxSpareThreads maximum number of worker threads which are kept spare # ThreadsPerChild constant number of worker threads in each server process # MaxRequestsPerChild maximum number of requests a server process serves IfModule worker.c StartServers 2 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadsPerChild 25 MaxRequestsPerChild 0 /IfModule 参考 http //httpd.apache.org/docs/2.2/ja/mod/worker.html 待ち受けポート番号 # # Listen Allows you to bind Apache to specific IP addresses and/or # ports, in addition to the default. See also the VirtualHost # directive. # # Change this to Listen on specific IP addresses as shown below to # prevent Apache from glomming onto all bound IP addresses (0.0.0.0) # #Listen 12.34.56.78 80 Listen 80 モジュール読み込み # # Dynamic Shared Object (DSO) Support # # To be able to use the functionality of a module which was built as a DSO you # have to place corresponding `LoadModule lines at this location so the # directives contained in it are actually available _before_ they are used. # Statically compiled modules (those listed by `httpd -l ) do not need # to be loaded here. # # Example # LoadModule foo_module modules/mod_foo.so # LoadModule auth_basic_module modules/mod_auth_basic.so LoadModule auth_digest_module modules/mod_auth_digest.so LoadModule authn_file_module modules/mod_authn_file.so #LoadModule authn_alias_module modules/mod_authn_alias.so LoadModule authn_anon_module modules/mod_authn_anon.so LoadModule authn_dbm_module modules/mod_authn_dbm.so LoadModule authn_default_module modules/mod_authn_default.so LoadModule authz_host_module modules/mod_authz_host.so LoadModule authz_user_module modules/mod_authz_user.so LoadModule authz_owner_module modules/mod_authz_owner.so LoadModule authz_groupfile_module modules/mod_authz_groupfile.so LoadModule authz_dbm_module modules/mod_authz_dbm.so LoadModule authz_default_module modules/mod_authz_default.so LoadModule ldap_module modules/mod_ldap.so LoadModule authnz_ldap_module modules/mod_authnz_ldap.so LoadModule include_module modules/mod_include.so LoadModule log_config_module modules/mod_log_config.so LoadModule logio_module modules/mod_logio.so LoadModule env_module modules/mod_env.so LoadModule ext_filter_module modules/mod_ext_filter.so LoadModule mime_magic_module modules/mod_mime_magic.so LoadModule expires_module modules/mod_expires.so LoadModule deflate_module modules/mod_deflate.so LoadModule headers_module modules/mod_headers.so LoadModule usertrack_module modules/mod_usertrack.so LoadModule setenvif_module modules/mod_setenvif.so LoadModule mime_module modules/mod_mime.so LoadModule dav_module modules/mod_dav.so LoadModule status_module modules/mod_status.so LoadModule autoindex_module modules/mod_autoindex.so LoadModule info_module modules/mod_info.so LoadModule dav_fs_module modules/mod_dav_fs.so LoadModule vhost_alias_module modules/mod_vhost_alias.so LoadModule negotiation_module modules/mod_negotiation.so LoadModule dir_module modules/mod_dir.so LoadModule actions_module modules/mod_actions.so LoadModule speling_module modules/mod_speling.so LoadModule userdir_module modules/mod_userdir.so LoadModule alias_module modules/mod_alias.so LoadModule rewrite_module modules/mod_rewrite.so LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_balancer_module modules/mod_proxy_balancer.so LoadModule proxy_ftp_module modules/mod_proxy_ftp.so LoadModule proxy_http_module modules/mod_proxy_http.so LoadModule proxy_connect_module modules/mod_proxy_connect.so LoadModule cache_module modules/mod_cache.so LoadModule suexec_module modules/mod_suexec.so LoadModule disk_cache_module modules/mod_disk_cache.so LoadModule file_cache_module modules/mod_file_cache.so LoadModule mem_cache_module modules/mod_mem_cache.so LoadModule cgi_module modules/mod_cgi.so LoadModule version_module modules/mod_version.so # # The following modules are not loaded by default # #LoadModule cern_meta_module modules/mod_cern_meta.so #LoadModule asis_module modules/mod_asis.so 外部設定ファイルの読み込み # # Load config files from the config directory "/etc/httpd/conf.d". # Include conf.d/*.conf 拡張ステータス情報保存の有無 # # ExtendedStatus controls whether Apache will generate "full" status # information (ExtendedStatus On) or just basic information (ExtendedStatus # Off) when the "server-status" handler is called. The default is Off. # #ExtendedStatus On 実行ユーザ・グループ # # If you wish httpd to run as a different user or group, you must run # httpd as root initially and it will switch. # # User/Group The name (or #number) of the user/group to run httpd as. # . On SCO (ODT 3) use "User nouser" and "Group nogroup". # . On HPUX you may not be able to use shared memory as nobody, and the # suggested workaround is to create a user www and use that user. # NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET) # when the value of (unsigned)Group is above 60000; # don t use Group #-1 on these systems! # User apache Group apache TOPへ編集 Section 2 Main server configuration ### Section 2 Main server configuration # # The directives in this section set up the values used by the main # server, which responds to any requests that aren t handled by a # VirtualHost definition. These values also provide defaults for # any VirtualHost containers you may define later in the file. # # All of these directives may appear inside VirtualHost containers, # in which case these default settings will be overridden for the # virtual host being defined. # サーバ管理者メールアドレス # # ServerAdmin Your address, where problems with the server should be # e-mailed. This address appears on some server-generated pages, such # as error documents. e.g. admin@your-domain.com # ServerAdmin root@localhost サーバ名 # # ServerName gives the name and port that the server uses to identify itself. # This can often be determined automatically, but we recommend you specify # it explicitly to prevent problems during startup. # # If this is not set to valid DNS name for your host, server-generated # redirections will not work. See also the UseCanonicalName directive. # # If your host doesn t have a registered DNS name, enter its IP address here. # You will have to access it by its address anyway, and this will make # redirections work in a sensible way. # #ServerName www.example.com 80 ServerName www.sapporobeer.co.jp 80 (サーバが自分自身の名前とポートを決定する方法の設定 # # UseCanonicalName Determines how Apache constructs self-referencing # URLs and the SERVER_NAME and SERVER_PORT variables. # When set "Off", Apache will use the Hostname and Port supplied # by the client. When set "On", Apache will use the value of the # ServerName directive. # UseCanonicalName Off ドキュメントルートの定義 # # DocumentRoot The directory out of which you will serve your # documents. By default, all requests are taken from this directory, but # symbolic links and aliases may be used to point to other locations. # DocumentRoot "/var/www/html" (調査・編集中) # # Each directory to which Apache has access can be configured with respect # to which services and features are allowed and/or disabled in that # directory (and its subdirectories). # # First, we configure the "default" to be a very restrictive set of # features. # Directory / Options FollowSymLinks AllowOverride None /Directory # # Note that from this point forward you must specifically allow # particular features to be enabled - so if something s not working as # you might expect, make sure that you have specifically enabled it # below. # ドキュメントルート配下に適用される設定 # # This should be changed to whatever you set DocumentRoot to. # Directory "/var/www/html" # # Possible values for the Options directive are "None", "All", # or any combination of # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews # # Note that "MultiViews" must be named *explicitly* --- "Options All" # doesn t give it to you. # # The Options directive is both complicated and important. Please see # http //httpd.apache.org/docs/2.2/mod/core.html#options # for more information. # Options Indexes FollowSymLinks ディレクトリインデックス作成の許可と、シンボリックリンクを辿ることの許可設定 # # AllowOverride controls what directives may be placed in .htaccess files. # It can be "All", "None", or any combination of the keywords # Options FileInfo AuthConfig Limit # AllowOverride None 分散設定ファイル（.htaccess）で許可するディレクティヴの種類の設定。 この場合はなし。 # # Controls who can get stuff from this server. # Order allow,deny Allow from all /Directory ユーザディレクトリモジュールの設定 # # UserDir The name of the directory that is appended onto a user s home # directory if a ~user request is received. # # The path to the end user account public_html directory must be # accessible to the webserver userid. This usually means that ~userid # must have permissions of 711, ~userid/public_html must have permissions # of 755, and documents contained therein must be world-readable. # Otherwise, the client will only receive a "403 Forbidden" message. # # See also http //httpd.apache.org/docs/misc/FAQ.html#forbidden # IfModule mod_userdir.c # # UserDir is disabled by default since it can confirm the presence # of a username on the system (depending on home directory # permissions). # UserDir disable ユーザディレクトリ機能は無効 # # To enable requests to /~user/ to serve the user s public_html # directory, remove the "UserDir disable" line above, and uncomment # the following line instead # #UserDir public_html /IfModule ユーザディレクトリ配下に適用される設定 # # Control access to UserDir directories. The following is an example # for a site where these directories are restricted to read-only. # # Directory /home/*/public_html # AllowOverride FileInfo AuthConfig Limit # Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec # Limit GET POST OPTIONS # Order allow,deny # Allow from all # /Limit # LimitExcept GET POST OPTIONS # Order deny,allow # Deny from all # /LimitExcept # /Directory ディレクトリインデックスの設定 # # DirectoryIndex sets the file that Apache will serve if a directory # is requested. # # The index.html.var file (a type-map) is used to deliver content- # negotiated documents. The MultiViews Option can be used for the # same purpose, but it is much slower. # DirectoryIndex index.html index.html.var 分散設定ファイルの設定 # # AccessFileName The name of the file to look for in each directory # for additional configuration directives. See also the AllowOverride # directive. # AccessFileName .htaccess (調査・編集中) # # The following lines prevent .htaccess and .htpasswd files from being # viewed by Web clients. # Files ~ "^\.ht" Order allow,deny Deny from all /Files MIMEタイプ設定ファイル # # TypesConfig describes where the mime.types file (or equivalent) is # to be found. # TypesConfig /etc/mime.types デフォルトのMIMEタイプの設定 # # DefaultType is the default MIME type the server will use for a document # if it cannot otherwise determine one, such as from filename extensions. # If your server contains mostly text or HTML documents, "text/plain" is # a good value. If most of your content is binary, such as applications # or images, you may want to use "application/octet-stream" instead to # keep browsers from trying to display binary files as though they are # text. # DefaultType text/plain MIME MAGICモジュールの設定 # # The mod_mime_magic module allows the server to use various hints from the # contents of the file itself to determine its type. The MIMEMagicFile # directive tells the module where the hint definitions are located. # IfModule mod_mime_magic.c # MIMEMagicFile /usr/share/magic.mime MIMEMagicFile conf/magic /IfModule DNSルックアップの設定 # # HostnameLookups Log the names of clients or just their IP addresses # e.g., www.apache.org (on) or 204.62.129.132 (off). # The default is off because it d be overall better for the net if people # had to knowingly turn this feature on, since enabling it means that # each client request will result in AT LEAST one lookup request to the # nameserver. # HostnameLookups Off メモリマッピングの有無 # # EnableMMAP Control whether memory-mapping is used to deliver # files (assuming that the underlying OS supports it). # The default is on; turn this off if you serve from NFS-mounted # filesystems. On some systems, turning it off (regardless of # filesystem) can improve performance; for details, please see # http //httpd.apache.org/docs/2.2/mod/core.html#enablemmap # #EnableMMAP off sendfileサポートの有無 # # EnableSendfile Control whether the sendfile kernel support is # used to deliver files (assuming that the OS supports it). # The default is on; turn this off if you serve from NFS-mounted # filesystems. Please see # http //httpd.apache.org/docs/2.2/mod/core.html#enablesendfile # #EnableSendfile off エラーログの設定 # # ErrorLog The location of the error log file. # If you do not specify an ErrorLog directive within a VirtualHost # container, error messages relating to that virtual host will be # logged here. If you *do* define an error logfile for a VirtualHost # container, that host s errors will be logged there and not here. # ErrorLog logs/error_log ログレベルの設定 # # LogLevel Control the number of messages logged to the error_log. # Possible values include debug, info, notice, warn, error, crit, # alert, emerg. # LogLevel warn ログフォーマットの設定 # # The following directives define some format nicknames for use with # a CustomLog directive (see below). # LogFormat "%h %l %u %t \"%r\" % s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined LogFormat "%h %l %u %t \"%r\" % s %b" common LogFormat "%{Referer}i - %U" referer LogFormat "%{User-agent}i" agent (調査・編集中) # "combinedio" includes actual counts of actual bytes received (%I) and sent (%O); this # requires the mod_logio module to be loaded. #LogFormat "%h %l %u %t \"%r\" % s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio カスタムログの設定 # # The location and format of the access logfile (Common Logfile Format). # If you do not define any access logfiles within a VirtualHost # container, they will be logged here. Contrariwise, if you *do* # define per- VirtualHost access logfiles, transactions will be # logged therein and *not* in this file. # #CustomLog logs/access_log common カスタムログファイルの設定 # # If you would like to have separate agent and referer logfiles, uncomment # the following directives. # #CustomLog logs/referer_log referer #CustomLog logs/agent_log agent カスタムログファイルの設定 # # For a single logfile with access, agent, and referer information # (Combined Logfile Format), use the following directive # CustomLog logs/access_log combined サーバ生成ドキュメントのフッタの設定 # # Optionally add a line containing the server version and virtual host # name to server-generated pages (internal error documents, FTP directory # listings, mod_status and mod_info output etc., but not CGI generated # documents or custom error documents). # Set to "EMail" to also include a mailto link to the ServerAdmin. # Set to one of On | Off | EMail # ServerSignature On アイコン画像ディレクトリの設定 # # Aliases Add here as many aliases as you need (with no limit). The format is # Alias fakename realname # # Note that if you include a trailing / on fakename then the server will # require it to be present in the URL. So "/icons" isn t aliased in this # example, only "/icons/". If the fakename is slash-terminated, then the # realname must also be slash terminated, and if the fakename omits the # trailing slash, the realname must also omit it. # # We include the /icons/ alias for FancyIndexed directory listings. If you # do not use FancyIndexing, you may comment this out. # Alias /icons/ "/var/www/icons/" アイコン画像ディレクトリに適用される設定 Directory "/var/www/icons" Options Indexes MultiViews AllowOverride None Order allow,deny Allow from all /Directory Web DAVモジュールの設定 # # WebDAV module configuration section. # IfModule mod_dav_fs.c # Location of the WebDAV lock database. DAVLockDB /var/lib/dav/lockdb /IfModule (調査・編集中) # # ScriptAlias This controls which directories contain server scripts. # ScriptAliases are essentially the same as Aliases, except that # documents in the realname directory are treated as applications and # run by the server when requested rather than as documents sent to the client. # The same rules about trailing "/" apply to ScriptAlias directives as to # Alias. # ScriptAlias /cgi-bin/ "/var/www/cgi-bin/" CGIディレクトリの設定 # # "/var/www/cgi-bin" should be changed to whatever your ScriptAliased # CGI directory exists, if you have that configured. # Directory "/var/www/cgi-bin" AllowOverride None Options None Order allow,deny Allow from all /Directory # # Redirect allows you to tell clients about documents which used to exist in # your server s namespace, but do not anymore. This allows you to tell the # clients where to look for the relocated document. # Example # Redirect permanent /foo http //www.example.com/bar # # Directives controlling the display of server-generated directory listings. # ディレクトリインデックスの設定 # # IndexOptions Controls the appearance of server-generated directory # listings. # IndexOptions FancyIndexing VersionSort NameWidth=* HTMLTable (調査・編集中) # # AddIcon* directives tell the server which icon to show for different # files or filename extensions. These are only displayed for # FancyIndexed directories. # AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip アイコン画像の設定（設定ごとの関連付け） AddIconByType (TXT,/icons/text.gif) text/* AddIconByType (IMG,/icons/image2.gif) image/* AddIconByType (SND,/icons/sound2.gif) audio/* AddIconByType (VID,/icons/movie.gif) video/* アイコン画像の設定（拡張子ごとの関連付け） AddIcon /icons/binary.gif .bin .exe AddIcon /icons/binhex.gif .hqx AddIcon /icons/tar.gif .tar AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip AddIcon /icons/a.gif .ps .ai .eps AddIcon /icons/layout.gif .html .shtml .htm .pdf AddIcon /icons/text.gif .txt AddIcon /icons/c.gif .c AddIcon /icons/p.gif .pl .py AddIcon /icons/f.gif .for AddIcon /icons/dvi.gif .dvi AddIcon /icons/uuencoded.gif .uu AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl AddIcon /icons/tex.gif .tex AddIcon /icons/bomb.gif core AddIcon /icons/back.gif .. AddIcon /icons/hand.right.gif README AddIcon /icons/folder.gif ^^DIRECTORY^^ AddIcon /icons/blank.gif ^^BLANKICON^^ デフォルトのアイコン画像の設定 # # DefaultIcon is which icon to show for files which do not have an icon # explicitly set. # DefaultIcon /icons/unknown.gif (調査・編集中) # # AddDescription allows you to place a short description after a file in # server-generated indexes. These are only displayed for FancyIndexed # directories. # Format AddDescription "description" filename # #AddDescription "GZIP compressed document" .gz #AddDescription "tar archive" .tar #AddDescription "GZIP compressed tar archive" .tgz (調査・編集中) # # ReadmeName is the name of the README file the server will look for by # default, and append to directory listings. # # HeaderName is the name of a file which should be prepended to # directory indexes. ReadmeName README.html HeaderName HEADER.html インデックス対象外の設定 # # IndexIgnore is a set of filenames which directory indexing should ignore # and not include in the listing. Shell-style wildcarding is permitted. # IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t 言語の設定 # # DefaultLanguage and AddLanguage allows you to specify the language of # a document. You can then use content negotiation to give a browser a # file in a language the user can understand. # # Specify a default language. This means that all data # going out without a specific language tag (see below) will # be marked with this one. You probably do NOT want to set # this unless you are sure it is correct for all cases. # # * It is generally better to not mark a page as # * being a certain language than marking it with the wrong # * language! # # DefaultLanguage nl # # Note 1 The suffix does not have to be the same as the language # keyword --- those with documents in Polish (whose net-standard # language code is pl) may wish to use "AddLanguage pl .po" to # avoid the ambiguity with the common suffix for perl scripts. # # Note 2 The example entries below illustrate that in some cases # the two character Language abbreviation is not identical to # the two character Country code for its country, # E.g. Danmark/dk versus Danish/da . # # Note 3 In the case of ltz we violate the RFC by using a three char # specifier. There is work in progress to fix this and get # the reference data for rfc1766 cleaned up. # # Catalan (ca) - Croatian (hr) - Czech (cs) - Danish (da) - Dutch (nl) # English (en) - Esperanto (eo) - Estonian (et) - French (fr) - German (de) # Greek-Modern (el) - Hebrew (he) - Italian (it) - Japanese (ja) # Korean (ko) - Luxembourgeois* (ltz) - Norwegian Nynorsk (nn) # Norwegian (no) - Polish (pl) - Portugese (pt) # Brazilian Portuguese (pt-BR) - Russian (ru) - Swedish (sv) # Simplified Chinese (zh-CN) - Spanish (es) - Traditional Chinese (zh-TW) # AddLanguage ca .ca AddLanguage cs .cz .cs AddLanguage da .dk AddLanguage de .de AddLanguage el .el AddLanguage en .en AddLanguage eo .eo AddLanguage es .es AddLanguage et .et AddLanguage fr .fr AddLanguage he .he AddLanguage hr .hr AddLanguage it .it AddLanguage ja .ja AddLanguage ko .ko AddLanguage ltz .ltz AddLanguage nl .nl AddLanguage nn .nn AddLanguage no .no AddLanguage pl .po AddLanguage pt .pt AddLanguage pt-BR .pt-br AddLanguage ru .ru AddLanguage sv .sv AddLanguage zh-CN .zh-cn AddLanguage zh-TW .zh-tw 言語優先順位の設定 # # LanguagePriority allows you to give precedence to some languages # in case of a tie during content negotiation. # # Just list the languages in decreasing order of preference. We have # more or less alphabetized them here. You probably want to change this. # LanguagePriority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl pt pt-BR ru sv zh-CN zh-TW (調査・編集中) # # ForceLanguagePriority allows you to serve a result page rather than # MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback) # [in case no accepted languages matched the available variants] # ForceLanguagePriority Prefer Fallback デフォルトの文字セットの設定 # # Specify a default charset for all content served; this enables # interpretation of all content as UTF-8 by default. To use the # default browser choice (ISO-8859-1), or to allow the META tags # in HTML content to override this choice, comment out this # directive # AddDefaultCharset UTF-8 (調査・編集中) # # AddType allows you to add to or override the MIME configuration # file mime.types for specific file types. # #AddType application/x-tar .tgz (調査・編集中) # # AddEncoding allows you to have certain browsers uncompress # information on the fly. Note Not all browsers support this. # Despite the name similarity, the following Add* directives have nothing # to do with the FancyIndexing customization directives above. # #AddEncoding x-compress .Z #AddEncoding x-gzip .gz .tgz (調査・編集中) # If the AddEncoding directives above are commented-out, then you # probably should define those extensions to indicate media types # AddType application/x-compress .Z AddType application/x-gzip .gz .tgz (調査・編集中) # # AddHandler allows you to map certain file extensions to "handlers" # actions unrelated to filetype. These can be either built into the server # or added with the Action directive (see below) # # To use CGI scripts outside of ScriptAliased directories # (You will also need to add "ExecCGI" to the "Options" directive.) # #AddHandler cgi-script .cgi (調査・編集中) # # For files that include their own HTTP headers # #AddHandler send-as-is asis (調査・編集中) # # For type maps (negotiated resources) # (This is enabled by default to allow the Apache "It Worked" page # to be distributed in multiple languages.) # AddHandler type-map var (調査・編集中) # # Filters allow you to process content before it is sent to the client. # # To parse .shtml files for server-side includes (SSI) # (You will also need to add "Includes" to the "Options" directive.) # AddType text/html .shtml AddOutputFilter INCLUDES .shtml (調査・編集中) # # Action lets you define media types that will execute a script whenever # a matching file is called. This eliminates the need for repeated URL # pathnames for oft-used CGI file processors. # Format Action media/type /cgi-script/location # Format Action handler-name /cgi-script/location # (調査・編集中) # # Customizable error responses come in three flavors # 1) plain text 2) local redirects 3) external redirects # # Some examples #ErrorDocument 500 "The server made a boo boo." #ErrorDocument 404 /missing.html #ErrorDocument 404 "/cgi-bin/missing_handler.pl" #ErrorDocument 402 http //www.example.com/subscription_info.html # # # Putting this all together, we can internationalize error responses. # # We use Alias to redirect any /error/HTTP_ error .html.var response to # our collection of by-error message multi-language collections. We use # includes to substitute the appropriate text. # # You can modify the messages appearance without changing any of the # default HTTP_ error .html.var files by adding the line # # Alias /error/include/ "/your/include/path/" # # which allows you to create your own set of files by starting with the # /var/www/error/include/ files and # copying them to /your/include/path/, even on a per-VirtualHost basis. # (調査・編集中) Alias /error/ "/var/www/error/" エラードキュメントの設定 IfModule mod_negotiation.c IfModule mod_include.c Directory "/var/www/error" AllowOverride None Options IncludesNoExec AddOutputFilter Includes html AddHandler type-map var Order allow,deny Allow from all LanguagePriority en es de fr ForceLanguagePriority Prefer Fallback /Directory # ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var # ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var # ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var # ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var # ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var # ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var # ErrorDocument 410 /error/HTTP_GONE.html.var # ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var # ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var # ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var # ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var # ErrorDocument 415 /error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var # ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var # ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var # ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var # ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var # ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var /IfModule /IfModule (調査・編集中) # # The following directives modify normal HTTP response behavior to # handle known problems with browser implementations. # BrowserMatch "Mozilla/2" nokeepalive BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0 BrowserMatch "RealPlayer 4\.0" force-response-1.0 BrowserMatch "Java/1\.0" force-response-1.0 BrowserMatch "JDK/1\.0" force-response-1.0 # # The following directive disables redirects on non-GET requests for # a directory that does not include the trailing slash. This fixes a # problem with Microsoft WebFolders which does not appropriately handle # redirects for folders with DAV methods. # Same deal with Apple s DAV filesystem and Gnome VFS support for DAV. # BrowserMatch "Microsoft Data Access Internet Publishing Provider" redirect-carefully BrowserMatch "MS FrontPage" redirect-carefully BrowserMatch "^WebDrive" redirect-carefully BrowserMatch "^WebDAVFS/1.[0123]" redirect-carefully BrowserMatch "^gnome-vfs/1.0" redirect-carefully BrowserMatch "^XML Spy" redirect-carefully BrowserMatch "^Dreamweaver-WebDAV-SCM1" redirect-carefully サーバステータス表示設定 # # Allow server status reports generated by mod_status, # with the URL of http //servername/server-status # Change the ".example.com" to match your domain to enable. # # Location /server-status # SetHandler server-status # Order deny,allow # Deny from all # Allow from .example.com # /Location サーバ情報表示設定 # # Allow remote server configuration reports, with the URL of # http //servername/server-info (requires that mod_info.c be loaded). # Change the ".example.com" to match your domain to enable. # # Location /server-info # SetHandler server-info # Order deny,allow # Deny from all # Allow from .example.com # /Location プロキシモジュールの設定 # # Proxy Server directives. Uncomment the following lines to # enable the proxy server # # IfModule mod_proxy.c #ProxyRequests On # # Proxy * # Order deny,allow # Deny from all # Allow from .example.com # /Proxy プロキシ経由アクセス時のViaヘッダの有効・無効の設定 # # Enable/disable the handling of HTTP/1.1 "Via " headers. # ("Full" adds the server version; "Block" removes all outgoing Via headers) # Set to one of Off | On | Full | Block # #ProxyVia On コンテンツキャッシュストレージ管理モジュールの設定 # # To enable a cache of proxied content, uncomment the following lines. # See http //httpd.apache.org/docs/2.2/mod/mod_cache.html for more details. # # IfModule mod_disk_cache.c # CacheEnable disk / # CacheRoot "/var/cache/mod_proxy" # /IfModule # # /IfModule # End of proxy directives. TOPへ編集 Section 3 Virtual Hosts ### Section 3 Virtual Hosts # # VirtualHost If you want to maintain multiple domains/hostnames on your # machine you can setup VirtualHost containers for them. Most configurations # use only name-based virtual hosts so the server doesn t need to worry about # IP addresses. This is indicated by the asterisks in the directives below. # # Please see the documentation at # URL http //httpd.apache.org/docs/2.2/vhosts/ # for further details before you try to setup virtual hosts. # # You may use the command line option -S to verify your virtual host # configuration. # # Use name-based virtual hosting. # #NameVirtualHost * 80 # # NOTE NameVirtualHost cannot be used without a port specifier # (e.g. 80) if mod_ssl is being used, due to the nature of the # SSL protocol. # # # VirtualHost example # Almost any Apache directive may go into a VirtualHost container. # The first VirtualHost section is used for requests without a known # server name. # # VirtualHost * 80 # ServerAdmin webmaster@dummy-host.example.com # DocumentRoot /www/docs/dummy-host.example.com # ServerName dummy-host.example.com # ErrorLog logs/dummy-host.example.com-error_log # CustomLog logs/dummy-host.example.com-access_log common # /VirtualHost 最終更新日 [2011-04-15]
https://w.atwiki.jp/katsuhiro/pages/26.html
HTTPメソッド GET情報取得メソッド POST PUT DELETEリソース削除メソッド HTTPリクエスト ポストデータ HTMLのPOST指定のformから送信されるデータ JSPのrequestオブジェクトから下記のメソッドで情報を取得できるgetParameter getParameterValues リクエストボディのセットされて送信される クエリ情報 URLの末尾の"?"以降に「キー＝値」のセットで付加される簡易な情報 複数のセットがある場合は" "で連結される URLに直接指定するほか、HTMLのGET指定のformから送信されるデータ formのmethod属性が省略された場合もクエリ情報として送信される JSPのrequestオブジェクトから下記のメソッドで情報を取得できるgetParameter クエリ情報に特殊文字が含まれる場合は、あらかじめエンコードしておく必要がある（form経由の場合はエンコード不要） URLに使用可能な文字数を超えて送信できない(2,083文字)FireFoxの場合は制限が無いが、動作が遅くなる場合もあるらしい データがアドレス欄に露出してしまう ヘッダ情報 「名前： 値」形式 種類一般ヘッダ（要求／応答時双方で利用） エンティティヘッダ（コンテンツに関する情報） リクエスト（要求）ヘッダ（クライアントに関する情報） レスポンス（応答）ヘッダ（その他） JSPのrequestオブジェクトから下記のメソッドで情報を取得できるgetHeaderNames ただし、情報取得専用メソッドが存在するヘッダについてはそちらを使う ■ヘッダ例 種類 ヘッダ名 概要 一般 Cache-Control キャッシュルールを規定する Connection プロキシ（中間）サーバで削除すべきHTTPヘッダを指定 Date コンテンツ生成日時 Pragma キャッシングを利用するか（下位互換用のヘッダ） Transfer-Encoding コンテンツの転送エンコーディング方式 リクエスト Accept クライアント対応コンテンツの種類（優先順） Accept-Language クライアント対応言語（優先順） Authorization 認証情報 Cookie クライアントに保存されたクッキーデータを送信 Host 要求先ホスト名 If-Modified-Since 指定日時以降にコンテンツが更新されている場合にのみ、サーバはデータを送信 Proxy-Authorization プロキシサーバ用の認証情報 Range 要求リソース範囲 Referer リンク元URI User-Agent クライアントの種類 レスポンス ETag リソースを一意に特定するためのキー情報（コンテンツが更新されていないかどうかを特定する場合などに使用） Location クライアントに新しいURIに移動するように促す Server サーバの種類 Set-Cookie クライアントにクッキーを送信 WWW-Authenticate クライアントに認証を要求 エンティティ Content-Encoding コンテンツのエンコーディング方式 Content-Length コンテンツサイズ Content-Type コンテンツの種類 Expires コンテンツの有効期限 Last-Modified コンテンツの最終更新年月日 クッキー サーバがクライアントに対して自由に読み書きできるテキスト クッキーの有効期限負数をセットした場合、ブラウザの終了時に削除される ０をセットした場合、その場で削除される １以上をセットすると、その秒数分保持される クッキーのデメリットクライアント側でクッキーを受け入れないように設定することが可能 クライアント側でクッキーの改竄や削除が可能 実データがネットワーク上を流れてしまう クッキーの制約1つのホスト、ドメイン当たりの最大個数は20個（総数では300個以内） クッキー1つあたりの最大サイズは4096バイト セッション情報 長期間にわたって情報を保持するには不向き ユーザがブラウザを開いている間だけアプリケーション内で情報を受け渡しする場合にはクッキーより手軽でセキュアな仕組み sessionJSPの暗黙オブジェクトの１つ 下記のメソッドを使って読み書きするgetAttribute setAttribute @pageディレクティブのsession属性がfalseの場合は使えない sessionが不要の場合はsession属性をfalseにしておく（サーバリソースの節約） sessionを使うと… クライアントからサーバにリクエスト送信 サーバからのレスポンスにSet-Cookieヘッダの値としてセッションIDが付加される(JSESSIONID) クライアントからサーバに2回目以降のリクエスト送信時、Cookieヘッダの値として、受け取ったJSESSIONIDを付加して送る サーバをそのセッションIDに該当するセッションを使って処理をし、レスポンスを返す セッションの破棄方法明示的な破棄(session.invalidate()) 有効期限を設定する(session.setMaxInactiveInteval()) web.xmlにセッションの有効期限を設定する session-config session-timeout セッションの寿命明示的に破棄されるか有効期限を過ぎない限り、クライアントを閉じてもサーバ上で生き続ける ieHTTPHeaders http //www.blunck.info/iehttpheaders/iehttpheaders.html ⇒IE上でHTTPによる通信内容をトレースするツール
https://w.atwiki.jp/testlink/pages/35.html
!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "DTD/xhtml1-transitional.dtd" !-- Japanese Translated by Testing Engineer s Forum (TEF) in Japan, Working Group of TestLink Japanese Translation Project -- html xmlns="http //www.w3.org/1999/xhtml" lang="jp" head !--20070421 - franciscom - using basehref smarty var to build right URLs BUGID 93 - 20050910 - fm--- meta http-equiv="Content-Type" content="text/html; charset=UTF-8" / meta http-equiv="Content-language" content="jp" / meta name="author" content="Martin Havlat" / meta name="copyright" content="GNU" / meta name="robots" content="NOFOLLOW" / title TestLink Help Content /title link rel="stylesheet" type="text/css" href="{$basehref}{$smarty.const.TL_THEME_CSS_DIR}tl_docs.css" / /head body {assign var="dummy" value="lib/general/show_help.php?locale=$locale help="}{assign var="help_launcher" value="$basehref$dummy"} h1 Help 目次 /h1 div id="menu" a href="javascript window.close();" class="tlButton" 閉じる /a a href="javascript history.back();" class="tlButton" 戻る /a /div ul li a href="{$help_launcher}glosary" 用語集 /a /li li a href="{$help_launcher}testproject" テストプロジェクト /a /li li a href="{$help_launcher}metrics" 結果とメトリクス /a /li li a href="{$help_launcher}shortcuts" ショートカット /a /li li a href="{$help_launcher}execMain" テスト実行 /a /li li a href="{$help_launcher}execFilter" テスト実行 - フィルター /a /li li a href="{$help_launcher}printFilter" テスト仕様フィルター /a /li li a href="{$help_launcher}testPlan" テスト計画 /a /li li a href="{$help_launcher}userRights" ユーザ権限 /a /li /ul h1 Instruction pages /h1 ul li a href="{$help_launcher}keywordsAssign" キーワード割り当て /a /li li a href="{$help_launcher}executeTest" テスト実行 /a /li li a href="{$help_launcher}planTesters" テスト計画 - テスター追加 /a /li li a href="{$help_launcher}planAddTC" テスト計画 - テストスイートにテストケース追加 /a /li li a href="{$help_launcher}planOwnerAndPriority" テスト計画 - 優先度 /a /li li a href="{$help_launcher}testSetRemove" テスト計画 - テストスイートからテストケース削除 /a /li li a href="{$help_launcher}planOwnerAndPriority" テスト計画 - 所有権 /a /li li a href="{$help_launcher}browseResults" テストレポートとメトリクス /a /li li a href="{$help_launcher}tcEdit" テスト仕様 - 編集 /a /li li a href="{$help_launcher}tcPrint" テスト仕様 - 印刷 /a /li li a href="{$help_launcher}tcSearch" テスト仕様 - 検索 /a /li /ul /body /html
https://w.atwiki.jp/dmtf/pages/14.html
1Scope The Common Information Model (CIM) (DSP0004) is an object-oriented information model defined by the Distributed Management Task Force (DMTF) that provides a conceptual framework for describing management data. The Common Information Model (CIM) (DSP0004) はDistributed Management Task Force (DMTF) によって定義されたデータ管理のためのオブジェクト指向データモデルです。 The Hypertext Transfer Protocol (HTTP) (RFC 1945, RFC 2068, RFC 2616) is an application-level protocol for distributed, collaborative, hypermedia information systems. This generic stateless protocol can be used for many tasks through extension of its request methods, error codes, and headers. The Hypertext Transfer Protocol (HTTP) (RFC 1945, RFC 2068, RFC 2616) は、ハイパーメディア情報システムを記述したり、コラボレートするためのアプリケーションレベルのプロトコル(規約)です。 この総括的なステートレスプロトコルはリクエストメソッド、エラーコードとヘッダをつかって多くのタスクに使用することが可能です。 The Extensible Markup Language (XML) is a simplified subset of SGML that offers powerful and extensible data modeling capabilities. An XML document is a collection of data represented in XML. An XML schema is a grammar that describes the structure of an XML document. The Extensible Markup Language (XML) Iはパワフルで拡張的なデータモデリングが可能なSGMLの簡素なサブセットです。XMLドキュメントはXMLで表現されたデータの集まりです。XMLスキーマはXMLドキュメントの構造を記述する文法です。 This document defines a mapping of CIM messages onto HTTP that allows implementations of CIM to interoperate in an open, standardized manner. It is based on the CIM XML DTD (DSP0201 and DSP0203) that defines the XML schema for CIM objects and messages. このドキュメントはHTTP上でやり取りされるのCIM実装で許容されたCIMメッセージと オープンで標準化されたマナーとしての相互運用（の規則）へのマッピングを定義します。
https://w.atwiki.jp/mydefrag_jp/pages/21.html
原文 http //www.mydefrag.com/Scripts-FileActions.html 更新日 2010/12/12 (ここで取り扱っている内容の原文をコピーした日付です) AddGap Set the position of the beginning of the next zone. This command is commonly used to create a gap at the end of the zone, making the zone bigger than necessary for the files in the zone, but the command can also be used to position a zone anywhere on disk. The command will be skipped (not executed) if the zone is empty (no files are selected by the FileBoolean). The NUMBER specifies the beginning of the next zone, an absolute position on the disk. Usually it will be the ZoneEnd plus a number of bytes, but you can specify a different formula. The command will do nothing if the NUMBER is negative. It is an absolute position on disk, and a negative number would be before the beginning of the disk. The program will automatically vacate the gap between the current end of the zone and the NUMBER. It will not vacate if the DoNotVacate option is specified, or if the NUMBER is lower than current end of the zone (negative gap). If all the next zones are sorted zones (using one of the SortBy fileactions) then DoNotVacate can be used, it will save some unnecessary data movements. The * FastFill and * MoveDownFill fileactions will only move files down, never up, so files that are in a DoNotVacate gap will be left in the gap. Syntax AddGap(NUMBER [, DoNotVacate]) Example # Add a gap of 1% of the free size of the volume. AddGap(ZoneEnd + VolumeFree * 0.01) # Same, but do not vacate. AddGap(ZoneEnd + VolumeFree * 0.01 , DoNotVacate) # Add a gap 1% of the volume size AddGap(ZoneEnd + VolumeSize * 0.01) # Add a gap of 1000 clusters. AddGap(ZoneEnd + 1000 * BytesPerCluster) # Add a gap 10% of the size of the MFT. AddGap(ZoneEnd + MftSize * 0.1) See also MakeGap FileActions Defragment Defragment all the selected items. Items that are not fragmented are ignored, they are not moved. Fragmented files are moved to somewhere above the beginning of the zone, possibly outside the zone. Defragment() will not optimize the zone, it does not move all files to the zone. To do that you need to use another fileaction, for example FastFill(). But not a SortBy fileaction, because those will already defragment all items and Defragment() would then do double work. There are 2 defragmentation algorithms to choose from. The * Fast algorithm will only defragment a file if it can find a gap big enough for the entire file. It will skip files that are too big for any gap. The default defragmentation algorithm will not give up so easily, if it encounters a big file and cannot find a big gap then it will try to make a big gap by shuffling other files around. This can take a lot of time. If the * IgnoreWrapAroundFragmentation setting is active (the default) then wrap-around fragmentation is not defragmented. Syntax Defragment(OPTIONS) Options Fast ChunkSize Example FileSelect .... FileActions Defragment() FileEnd See also IgnoreWrapAroundFragmentation FileSelect FileBoolean FileActions FastFill Fill gaps as best as possible with items from above the gap, in other words, consolidate free space. FastFill is a very fast and effective way to reduce the number of gaps on the disk, and at the same time move files as far to the beginning of the disk as possible. FastFill tries to perfectly fill gaps by looking for combinations of files. If no combination can be found and without the * WithShuffling option then the largest file that fits in the gap will be used, leaving a smaller gap. If all files above the gap are larger than the gap then the gap cannot be filled and will be skipped. If the WithShuffling option is specified then the file just above the gap will be moved away, making the gap bigger. The program will then try again to find a perfect fit. When looking for a combination of perfectly fitting files the program does not test all combinations of all files. It has to limit itself because the number of permutations for even a small set of files is astronomical. There is a tendency for small files to migrate to the beginning of the zone and large files to the end. This is because small files have a better chance to fit into a gap and are therefore more likely to move down. FastFill will destroy the ordering of the files. If the zone was optimized earlier (in another MyDefrag session, running another script) by one of the SortBy actions, then consider using * MoveDownFill instead. It is slower but it will preserve the ordering. Syntax FastFill() Options WithShuffling Example FileSelect .... FileActions # Fill gaps with items from above. FastFill() FileEnd See also WithShuffling MoveDownFill ForcedFill FileSelect FileBoolean FileActions ForcedFill Move all data as fast as possible to the beginning of the zone. The function will take the highest data on disk and split it into fragments that perfectly fill the gaps at the beginning of the zone, until the first gap is after the last data. Syntax ForcedFill() Example FileSelect .... FileActions # Fill gaps with items from above. ForcedFill() FileEnd See also MoveDownFill FastFill FileSelect FileBoolean FileActions MoveDownFill Fill all the gaps by moving (shifting) items to the beginning of the zone. This will perfectly fill all the gaps and will preserve the sorting order of the files. A tiny little gap somewhere at the beginning of the zone will cause all items above the gap to be moved (shifted). In this case MoveDownFill() is only a little faster than a full SortBy***(). However, if the gap happens to be further into the zone then MoveDownFill() will save time. Syntax MoveDownFill() Example FileSelect .... FileActions # Fill gaps with items from above. MoveDownFill() FileEnd See also FastFill ForcedFill FileSelect FileBoolean FileActions MoveToEndOfDisk Move the selected files to the end of the disk. More specifically for every selected file try to find a gap above that file big enough to hold the file, and move the file to the end of that gap. If no gap is found then skip the file. Files are automatically defragmented when they are moved. This action is relatively slow, best to be used for big files only. It s because the Microsoft defragmentation API is not very efficient in finding the last gap suitable for a file. The end of the disk is the slowest part of the disk. Many people want to move the spacehogs zone (with less important files that take up a lot of space) to the end of the disk, leaving a huge empty gap between the regular files and the spacehogs. In my opinion this is a waste of perfectly good harddisk space and makes the spacehogs slower than they need to be. This is why the standard MyDefrag scripts do not move the spacehogs to the end of the disk. Syntax MoveToEndOfDisk() Example FileSelect .... FileActions # Move files to the end of the disk. MoveToEndOfDisk() FileEnd See also FileSelect FileBoolean FileActions MoveUpToZone Move the selected files to above the beginning of the zone. Files that are already above the beginning of the zone are not moved. If there is no gap above the beginning of the zone that is big enough for a particular file, then the file is not moved. Files are automatically defragmented when they are moved. This action is designed to be used in cases where the beginning of the zone has been moved upwards by a * MakeGap volumeaction and the other fileactions would not move all the files. An example is the * FastFill fileaction, which only moves files down, never up, so files could stay before the beginning of the zone. MoveUpToZone() is not needed in zones that use a SortBy fileaction, because those actions will already move all files to the zone, even files that are before the beginning of the zone. Syntax MoveUpToZone() Example # Place the next zone at 50% of the volume. MakeGap(VolumeSize * 0.5, DoNotVacate) # Select files for the zone. FileSelect .... FileActions # Make sure all files are above the beginning of the zone. MoveUpToZone() # FastFill gaps in the zone with files from above the zone. FastFill() FileEnd See also FileSelect FileBoolean FileActions PlaceNtfsSystemFiles Place the selected items and sort alphabetically by their full pathname, ascending from A to Z or descending from Z to A. This function is intended to be used together with the * SelectNtfsSystemFiles fileboolean. It is basically the same as the * SortByName fileaction, except that files can be placed inside the NTFS reserved area. MyDefrag does not (cannot) change the size or location of the NTFS reserved area. The NUMBER parameter is only used to create a gap after the MFT. When Windows is booted it will automatically re-allocate the NTFS area. First it tries to place the area just after the MFT, using whatever free gap is there up to a maximum of 12.5% of the size of the volume. If there is no gap after the MFT then Windows places the area elsewhere on disk. Windows will also reset the area when the disk is mounted, see the MyDefrag * DismountVolume action. So, to move the NTFS reserved area you have to immediately boot the computer after using MyDefrag, and even then it is not guaranteed that the NTFS reserved area will have the size and place that you want. If the MFT is not selected then the NUMBER is ignored. It is useless to combine this fileaction with other fileactions, such as "Defragment()" or "FastFill()", because it moves all the files in the zone. Another fileaction would either needlessly move files, or would destroy the sorted order of the files. Syntax PlaceNtfsSystemFiles(OPTIONS , NUMBER) The OPTIONS are a space-separated list of these keywords Ascending Descending SkipBlock The NUMBER parameter is a hint, specifying a desired size for the NTFS reserved area. Example FileSelect # Select all the NTFS system files. SelectNtfsSystemFiles(yes) FileActions # Place the NTFS system files, NTFS reserved area is 10% of the MFT. PlaceNtfsSystemFiles(Ascending,MftSize * 0.1) FileEnd See also SelectNtfsSystemFiles DismountVolume ReclaimNtfsReservedAreas AppendLogfile BatteryPower Debug Description DiskmapFlip ExcludeFiles ExcludeVolumes ExitIfTimeout FileMoveChunkSize IgnoreWrapAroundFragmentation Language MaxRunTime Message OtherInstances Pause ProcessPriority RememberUnmovables RunProgram RunScript SetColor SetFileColor SetScreenPowerSaver SetScreenSaver SetStatisticsWindowText SetVariable Slowdown StatusBar Title WhenFinished WindowSize WriteLogfile ZoomLevel SortByCreationDate Place the selected items and sort by the time they were created, from oldest to newest ("ascending") or from newest to oldest ("descending"). The creation date can be newer than the last-changed date, for example when a file was downloaded, or unpacked from an archive (such as zip or arj). This action will also defragment. It is therefore not necessary to combine it with the * Defragment action. This action will create "wrap around" fragments. For more information see the * IgnoreWrapAroundFragmentation setting. Syntax SortByCreationDate(OPTIONS) The OPTIONS are a space-separated list of these keywords Ascending Descending SkipBlock Example FileSelect .... FileActions # Sort the items by CreationDate time, most recently accesses items first. SortByCreationDate(Descending) FileEnd See also FileSelect FileBoolean FileActions SortByImportSequence Place the selected items and sort by the sequence in which they were imported ("ascending") or in reversed order ("descending"). This function is designed to be used in combination with the * ImportListFromBootOptimize or the * ImportListFromFile file boolean. This action will also defragment. It is therefore not necessary to combine it with the * Defragment action. This action will create "wrap around" fragments. For more information see the * IgnoreWrapAroundFragmentation setting. Syntax SortByImportSequence(OPTIONS) The OPTIONS are a space-separated list of these keywords Ascending Descending SkipBlock Example # Optimize the system disk for faster booting. FileSelect ImportListFromBootOptimize() FileActions SortByImportSequence(Ascending) FileEnd See also ImportListFromBootOptimize ImportListFromFile FileSelect FileBoolean FileActions SortByLastAccess Place the selected items and sort by their LastAccess time from oldest to newest ("ascending") or from newest to oldest ("descending"). Sorting by LastAccess date/time may seem like a good idea at first, but is far from perfect. The theory is that the LastAccess times will be the same on all the files that are used by an application, so sorting by LastAccess will put all the files of the application together on disk. But the LastAccess time is also updated in many other cases, not only when you run an application. In my view sorting by LastAccess can be useful in certain situations, but is essentially random and should not be used for the bulk of the data on regular disks. Sorting in "Ascending" order will put the oldest (never accessed) files at the beginning of the zone. So, the files that you use the most are placed at the end of the zone, which is a slower part of the harddisk and (usually) further away from the MFT and the directories. Sorting in "Descending" order will put the last accessed files at the beginning of the zone. So, the files that are accessed first when you start a program are placed behind files that are accessed later. Your harddisk will be working backwards. Vista by default does not update the LastAccess time. For more information see * What is "NtfsDisableLastAccessUpdate"? On FAT volumes the resolution of the LastAccess time is 1 day. NTFS delays updates to the LastAccess time by up to one hour. Some improperly programmed utilities cause a change in the LastAccess time of all items on the disk when they scan the disk. Examples are virus scanners, backup programs, text indexers. This action will also defragment. It is therefore not necessary to combine it with the * Defragment action. This action will create "wrap around" fragments. For more information see the * IgnoreWrapAroundFragmentation setting. Syntax SortByLastAccess(OPTIONS) The OPTIONS are a space-separated list of these keywords Ascending Descending SkipBlock Example FileSelect .... FileActions # Sort the items by LastAccess time, most recently accesses items first. SortByLastAccess(Descending) FileEnd See also FileSelect FileBoolean FileActions SortByLastChange Place the selected items and sort by the time they were last changed, from oldest to newest ("ascending") or from newest to oldest ("descending"). The last-changed date can be older than the creation date, for example when a file was downloaded, or unpacked from an archive (such as zip or arj). This action will also defragment. It is therefore not necessary to combine it with the * Defragment action. This action will create "wrap around" fragments. For more information see the * IgnoreWrapAroundFragmentation setting. Syntax SortByLastChange(OPTIONS) The OPTIONS are a space-separated list of these keywords Ascending Descending SkipBlock Example FileSelect .... FileActions # Sort the items by LastChange time, most recently accesses items first. SortByLastChange(Descending) FileEnd See also FileSelect FileBoolean FileActions SortByName Place the selected items and sort alphabetically by their full pathname, ascending from A to Z or descending from Z to A. Items are not just sorted by their filename (for example "explorer.exe"), but by their full pathname including all the folder names (for excample "c \windows\explorer.exe"). The result is that all items that are in the same folder are placed in a block together on disk, and inside that block they re sorted by their filename. If a file has multiple names (hard links) then the file is sorted by the first name that happens to be mentioned in the FAT/MFT. This action will also defragment. It is therefore not necessary to combine it with the * Defragment action. This action will create "wrap around" fragments. For more information see the * IgnoreWrapAroundFragmentation setting. Syntax SortByName(OPTIONS) The OPTIONS are a space-separated list of these keywords Ascending Descending SkipBlock Example FileSelect .... FileActions # Sort the items by their full path. SortByName(Ascending) FileEnd See also FileSelect FileBoolean FileActions SortByNewestDate Place the selected items and sort by creation, last access, or last change date/time, whichever is newest, from oldest to newest ("ascending") or from newest to oldest ("descending"). Sorting by newest date/time may seem like a good idea at first, but is far from perfect. The theory is that the newest date/times will be the same on all the files that are used by an application, so sorting by the newest time will put all the files of the application together on disk. But the date/times are also updated in many other cases, not only when you run an application. In my view sorting by newest date/time can be useful in certain situations, but is essentially random and should not be used for the bulk of the data on regular disks. Sorting in "Ascending" order will put the oldest files at the beginning of the zone. So, the files that you use the most are placed at the end of the zone, which is a slower part of the harddisk and (usually) further away from the MFT and the directories. Sorting in "Descending" order will put the newest files at the beginning of the zone. So, the files that are accessed first when you start a program are placed behind files that are accessed later. Your harddisk will be working backwards. The creation date can be newer than the last-changed date, for example when a file was downloaded, or unpacked from an archive (such as zip or arj). This action will also defragment. It is therefore not necessary to combine it with the * Defragment action. This action will create "wrap around" fragments. For more information see the * IgnoreWrapAroundFragmentation setting. Syntax SortByNewestDate(OPTIONS) The OPTIONS are a space-separated list of these keywords Ascending Descending SkipBlock Example FileSelect .... FileActions # Sort the items by newest time. SortByNewestDate(Descending) FileEnd See also FileSelect FileBoolean FileActions SortBySize Place the selected items and sort by size from smallest to largest ("ascending") or from largest to smallest ("descending"). This action will also defragment. It is therefore not necessary to combine it with the * Defragment action. This action will create "wrap around" fragments. For more information see the * IgnoreWrapAroundFragmentation setting. Syntax SortBySize(OPTIONS) The OPTIONS are a space-separated list of these keywords Ascending Descending SkipBlock Example FileSelect .... FileActions # Sort the items from smallest to largest. SortBySize(Ascending) FileEnd See also FileSelect FileBoolean FileActions
https://w.atwiki.jp/testlink/pages/49.html
!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "DTD/xhtml1-transitional.dtd" !-- Japanese Translated by Testing Engineer s Forum (TEF) in Japan, Working Group of TestLink Japanese Translation Project -- html xmlns="http //www.w3.org/1999/xhtml" lang="jp" head meta http-equiv="Content-Type" content="text/html; charset=UTF-8" / meta http-equiv="Content-language" content="jp" / meta name="author" content="Martin Havlat" / meta name="copyright" content="GNU" / meta name="robots" content="NOFOLLOW" / title TestLink Help Print Test Cases /title link rel="stylesheet" type="text/css" href="../../{$smarty.const.TL_THEME_CSS_DIR}tl_docs.css" / /head body h1 テストケース印刷のフィルタリング /h1 {include file="nav.tpl"} p この表により表示するテストケースをフィルタリングすることができます。選択したデータを表示します。チェックを変更したり、"フィルター"ボタンをクリックしたり、必要なデータのレベルをツリーから選択したりすることで表示するデータを切り替えることができます。 /p h2 ドキュメントのヘッダ /h2 p ドキュメントのヘッダ情報をフィルタリングすることもできます。ドキュメントのヘッダ情報には以下のものが含まれます イントロダクション、スコープ、参照、テスト手法、テストの制限事項。 /p h2 テストケース本体 /h2 p テストケース本体に含まれる情報をフィルタリングすることもできます。テストケース本体には以下の情報が含まれます 概要、ステップ、実行結果、キーワード。 /p h2 テストケースの概要 /h2 p テストケースのタイトルから、テストケースの概要情報をフィルタリングすることもできます。しかし、テストケース本体から概要をフィルタリングすることはできません。テストケースのタイトルを表示するときに、概要のみを表示して、その他のステップ、実行結果、キーワードを非表示にすることはできます。しかし、テストケース本体を表示するときには必ずテスト概要は表示されます。 /p h2 目次 /h2 p テストリンクは全てのタイトルのリストを内部のハイパーリンク付きで挿入します。 /p h2 出力形式 /h2 p HTMLとMS Wordの２種類の形式で出力することができます。後者の場合、ブラウザがMS Wordのコンポーネントを自動で読み込み、ドキュメントを表示します。 /p /body /html
https://w.atwiki.jp/hitkik/pages/23.html
Windows で、HTTPでのやり取りを眺めるツール。 HTTP debug tool IE ---- Fiddler2 http //www.fiddler2.com/Fiddler2/firstrun.asp extension http //www.fiddler2.com/fiddler2/extensions.asp Firefox ---- Firebug 文字コード明示 html lang="ja" まず、 html の中で使用言語を示します。ja は日本語を示します。 日本語以外では en (英語)、fr (フランス語)、de (ドイツ語)、zh (中国語) などがあります。 meta http-equiv="Content-Type" content="text/html; charset=Shift_JIS" METAタグのContent-typeを明示すると同時に文字コードも明示します。 Shift_JIS 以外は EUC-JP, iso-2022-jp (JIS), UTF-8(Unicode) などがあります。 Shift_JIS はアンダーバー。EUC-JP と iso-2022-jp, UTF-8はハイフンです。 × content="text/html;" charset="Shift_JIS" ○ content="text/html; charset=Shift_JIS" 行間を広げる BODY STYLE="line-height 150%" line-heightの活用 div style="font 900 46pt;line-height 6pt;" div style="color #404040;text-indent 50px;" abc /div div style="color #808080;text-indent 100px;" def /div div style="color red;text-indent 150px;" ghi /div /div スタイルシートを使ったテキストフィルタ http //www.tohoho-web.com/css/filter.htm スタイルシートクイックレファレンス http //www.htmq.com/style/index.shtml 以下広告
https://w.atwiki.jp/cod4mod/pages/33.html
MP Game Script Files (.gsc) The purpose of this section is to outline what is needed to create the .gsc files used in a multiplayer map. この項の目的は何がマルチプレ-ヤーマップで使われた .gsc ファイルを作るために必要とされるかについて概説することです。 Creating the level.gsc file The first step is to create a game script file with your level s name in the filename. It goes in the following game directory 第１ステップはファイル名であなたのレベルの名前でゲームスクリプトファイルを作成するはずです。それは次のゲームディレクトリに入ります： \raw\maps\mp\mp_yourmap.gsc Below is a screenshot of the mp_backlot.gsc file, opened in UltraEdit. It can be opened in any text editing application. Below the image is a breakdown of each of the lines in the script file. 下は、 UltraEdit で開かれて、 mp_backlot.gsc ファイルのスクリーンショットです。それはどんなテキスト編集アプリケーションででも開かれることができます。スクリプトファイルで画像の下にラインのそれぞれの内訳があります。 maps\mp\mp_backlot_fx main(); This is a reference to the special FX file for the map. Only needed if the map_fx.gsc file exists. maps\createart\mp_backlot_art main(); This is a reference to the Art file for the map. The map_art.gsc files don t exist in the community tools, so in a user-made map this line wouldn t exist. maps\mp\_load main(); Required for map to run. maps\mp\_compass setupMiniMap("compass_map_mp_backlot"); This line is needed for the minimap image to display correctly. maps\mp\mp_backlot_fx main(); これはマップのための特別な FX ファイルにレファレンスです。ただ、もし map_fx.gsc ファイルが存在するなら、必要とされるだけです。 maps\createart\mp_backlot_art main(); これはマップのための絵画写真資料フィルムにレファレンスです。map_art.gsc ファイルはコミュニティツールで存在しません、それでユーザ製のマップでこのラインは存在しないでしょう。 maps\mp\_load main(); マップのために稼働するために必要とされる。 maps\mp\_compass setupMiniMap("compass_map_mp_backlot"); このラインは正確に表示部にミニマップイメージのために必要です。 //setExpFog(500, 2200, 0.81, 0.75, 0.63, 0); This line creates exponential fog for the map (start distance, end distance, red, green, blue, transition time). It is commented out because it was later redefined in the map_art.gsc file. It should be uncommented in a user-made map. //VisionSetNaked( "mp_backlot" ); This line references the map s .vision file for post-processed color correction. It is commented out because it was later redefined in the map_art.gsc file. It should be uncommented in a user-made map with a .vision file. ambientPlay("ambient_backlot_ext"); Plays the ambient sound track created for this map. //setExpFog(500, 2200, 0.81, 0.75, 0.63, 0); このラインはマップ（スタートディスタンス、終わりディスタンス、赤い、緑の、青い、遷移時間）を求めて指数のフォグを作ります。 //VisionSetNaked( "mp_backlot" ); この行マップが（そのために） .vision ファイルであるリファレンスが色補正をポスト - 処理しました。それが map_art.gsc ファイルで後に再定義されたから、それはコメントアウトされます。それは .vision ファイルでユーザ製のマップで uncommented されるべきです。 ambientPlay("ambient_backlot_ext"); 周囲のサウンドトラックがこのマップを求めて作った活動。 game["allies"] = "marines"; Sets the "friendly" team to Marines. game["axis"] = "opfor"; Sets the "enemy" team to the OpFor desert enemies. game["attackers"] = "axis"; Sets the attacking team in Search and Destroy to the "enemy" team. game["defenders"] = "allies"; Sets the defending team in Search and Destroy to the "friendly" team. game["allies_soldiertype"] = "desert"; The Marines in this map will be using desert gear. game["axis_soldiertype"] = "desert"; The OpFor in this map will also be using desert gear. game["allies"] = "marines"; フレンドリー」チームを海兵隊員に設定します。 game["axis"] = "opfor"; 「敵の」チームを OpFor 砂漠の敵に設定します。 game["attackers"] = "axis"; Search and Destroy の攻撃しているチームを「敵の」チームに設定します。 game["defenders"] = "allies"; Search and Destroy の防御しているチームを「フレンドリー」チームに設定します。 game["allies_soldiertype"] = "desert"; このマップの海兵隊員が砂漠のギアを使ってであろう。 game["axis_soldiertype"] = "desert"; このマップの OpFor が同じく砂漠のギアを使ってであろう。 setdvar( "r_specularcolorscale", "1" ); This value is defined in some maps to make surfaces more reflective. (To simulate wet surfaces in maps like Downpour, for instance). It has to be zeroed out to 1 in all other maps so it won t stay at the reflective value on a map switch. setdvar( "r_specularcolorscale", "1" ); この値は表面をいっそう反射させるために若干のマップで定義されます。（Downpour のようなマップで、実例を求めて濡れた表面を装うために）。それはすべての他のマップで１にゼロで置き換えられなければなりません、それでそれはマップスイッチの上に反射する値に滞在しないでしょう。 setdvar("r_glowbloomintensity0",".25"); These three values are values used to tweak the bloom effect, when bloom is enabled. Not necissarily needed for user-made map. setdvar("r_glowbloomintensity1",".25"); setdvar("r_glowskybleedintensity0",".3"); setdvar("compassmaxrange","1800"); Sets the display distance of the minimap. setdvar("r_glowbloomintensity0",".25"); 値が、ブルームが使用可能であるとき、ブルーム効果を微調整するために使ったこれらの３つの値がそうである。 setdvar("r_glowbloomintensity1",".25"); setdvar("r_glowskybleedintensity0",".3"); setdvar("compassmaxrange","1800"); ミニマップの表示距離を設定します。 Creating the level_fx.gsc file The level_fx.gsc file is optional, but can be used to add special effects to your level. It goes in the following game directory level_fx.gsc ファイルはオプションです、しかしあなたのレベルに特殊効果を加えるために使われることができます。それは次のゲームディレクトリに入ります： \raw\maps\mp\mp_yourmap_fx.gsc Below is a screenshot of the mp_backlot_fx.gsc file, opened in UltraEdit. It can be opened in any text editing application. 下は、 UltraEdit で開かれて、 mp_backlot_fx.gsc ファイルのスクリーンショットです。それはどんなテキスト編集アプリケーションででも開かれることができます。 Each of these lines is loading a special effect into memory under a certain alias, which can then be referenced when defining an effect as described below. これらのラインのそれぞれがそれから、下に記述されるように、結果を明確にするとき、参照されることができるあるエイリアスの下のメモリに特殊効果を載せています。 The maps that shipped with the game have a separate map_art.gsc file where these effects were defined. User-made maps won t have this file, so the effects should be defined within the map_fx.gsc file. ゲームで出荷されたマップはこれらの結果が明確にされた別個の map_art.gsc ファイルを持っています。ユーザ製のマップがこのファイルを持たないでしょう、それで結果は map_fx.gsc ファイルの中で明確にされるべきです。 Names of special FX that you can use are located in the \raw\fx directory. あなたが使うことができる特別な FX の名前は \raw\fx ディレクトリに置かれています。 Below are a few examples of what these definitions would look like. 下は定義が見えるであろうこれらを望むものの少数の例です。 Defining a looping sound at certain point in the map ent = maps\mp\_createfx createLoopSound(); ent.v[ "origin" ] = ( -619.675, -2705.93, 331.715 ); ent.v[ "angles" ] = ( 270, 0, 0 ); ent.v[ "soundalias" ] = "emt_tree_palm_rustle"; Defining a one-shot effect ent = maps\mp\_utility createOneshotEffect( "firelp_small_pm" ); ent.v[ "origin" ] = ( -187.003, -703.577, 67.8959 ); ent.v[ "angles" ] = ( 270, 30.6197, 101.38 ); ent.v[ "fxid" ] = "firelp_small_pm"; ent.v[ "delay" ] = -15; ent.v[ "soundalias" ] = "fire_metal_small"; A one-shot effect places a certain effect at the specified location in a map. The effect file itself is generally set to looping, so a placed one-shot effect will generally loop. １ショットの効果がある効果を指定されたロケーションにおいてマップに置きます。ループすることに、効果ファイル自身は一般に設定されます、それで出された１ショットの効果が一般にループするでしょう。 (Original "http //www.infinityward.com/wiki/index.php?title=MP_Game_Script_Files") 名前 すべて読む
https://w.atwiki.jp/godspeed/pages/43.html
files Header Banner Icon Button